Error Messages

Error messages can come from:

An error reported on an ODBC driver has the following format: 

[vendor] [ODBC_component] message

ODBC_component is the component in which the error occurred. For example, an error message from the Sybase driver would look like this: 

[DataDirect] [ODBC Sybase driver]
Invalid precision specified.

If you receive this type of error, check the last ODBC call made by your application for possible problems or contact your ODBC application vendor.

An error that occurs in the data source includes the data store name, in the following format: 

[vendor] [ODBC_component] [data_store] message

With this type of message, ODBC_component is the component that received the error from the data store indicated. For example, you may receive the following message from an Oracle data store: 

[DataDirect] [ODBC Sybase driver] [Sybase]
specified length too long for CHAR column

If you receive this type of error, something is incorrect regarding the database system. Check your database system documentation for more information or consult your database administrator. In this example, you would check your Oracle documentation.

The driver manager is a DLL that establishes connections with drivers, submits requests to drivers, and returns results to applications. An error that occurs in the driver manager has the following format: 

[vendor] [ODBC XXX] message

For example, an error from the Microsoft driver manager might look like this: 

[Microsoft] [ODBC Driver Manager]
Driver does not support this function

If you receive this type of error, consult the Programmer’s Reference for the Microsoft ODBC Software Development Kit available from Microsoft.